Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfacd22a2d3a4ba7192b25bd59597eaa8967d7b031b1ec74d8ce4e9aab52f43f

Tx prefix hash: dfc1fc72d7f9adf3745fec2958e18e8665618caa655807a9953c2d5a1beebe9c
Tx public key: 7b2f7e6fc97cdb68186bf6e81cf8d0a1b6db7013628d711d5595c84b6b0f926f
Timestamp: 1649545865 Timestamp [UCT]: 2022-04-09 23:11:05 Age [y:d:h:m:s]: 03:209:11:12:41
Block: 476868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 927853 RingCT/type: yes/0
Extra: 017b2f7e6fc97cdb68186bf6e81cf8d0a1b6db7013628d711d5595c84b6b0f926f02110000000350e68f09000000000000000000

1 output(s) for total of 16.141303299000 dcy

stealth address amount amount idx
00: 8051ffc2e150bc6290f54128a56ce6383ce2b7aa1157d002bc6c2600a17caad4 16.141303299000 897447 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": 476878, "vin": [ { "gen": { "height": 476868 } } ], "vout": [ { "amount": 16141303299, "target": { "key": "8051ffc2e150bc6290f54128a56ce6383ce2b7aa1157d002bc6c2600a17caad4" } } ], "extra": [ 1, 123, 47, 126, 111, 201, 124, 219, 104, 24, 107, 246, 232, 28, 248, 208, 161, 182, 219, 112, 19, 98, 141, 113, 29, 85, 149, 200, 75, 107, 15, 146, 111, 2, 17, 0, 0, 0, 3, 80, 230, 143, 9, 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