Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 41ec97b0f1eb41d91fea9bfb5d61b05fcda7810bfb85aa2f79ad909de480d0bb

Tx prefix hash: 26d3b9d6cff1f5e3d0f862f2cbdfee98f3359852b564e3fa3369fdcee12ce1ad
Tx public key: e885d43b2deae9bcac1aaa523f9f2aab6f9710db8cc1e61e9e82cb0f45cdd496
Timestamp: 1630598441 Timestamp [UCT]: 2021-09-02 16:00:41 Age [y:d:h:m:s]: 03:155:22:41:13
Block: 326024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 885960 RingCT/type: yes/0
Extra: 01e885d43b2deae9bcac1aaa523f9f2aab6f9710db8cc1e61e9e82cb0f45cdd49602110000002a0441b428000000000000000000

1 output(s) for total of 51.020839632000 dcy

stealth address amount amount idx
00: 7b4cfa5e06dd9aeebcc600937bf4ae4bb0070b65dc7edab1f4d29c890083a481 51.020839632000 675609 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 326034, "vin": [ { "gen": { "height": 326024 } } ], "vout": [ { "amount": 51020839632, "target": { "key": "7b4cfa5e06dd9aeebcc600937bf4ae4bb0070b65dc7edab1f4d29c890083a481" } } ], "extra": [ 1, 232, 133, 212, 59, 45, 234, 233, 188, 172, 26, 170, 82, 63, 159, 42, 171, 111, 151, 16, 219, 140, 193, 230, 30, 158, 130, 203, 15, 69, 205, 212, 150, 2, 17, 0, 0, 0, 42, 4, 65, 180, 40, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8