Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81b73028eafadf9969a9ee1b52bcfdb9a627571c76d2387396ca0fccf9e34300

Tx prefix hash: cfd1211a58cb15bbb1f69e397b3bd1b7069ee8ec8303c0acd0fb2b9dbf7f3e4a
Tx public key: 1a75f67f36f8742b7e6dadc841e1f8bbcc0acbf3326e3cafe7b55dd40304b4a3
Timestamp: 1627957066 Timestamp [UCT]: 2021-08-03 02:17:46 Age [y:d:h:m:s]: 03:155:23:58:37
Block: 306229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 884211 RingCT/type: yes/0
Extra: 011a75f67f36f8742b7e6dadc841e1f8bbcc0acbf3326e3cafe7b55dd40304b4a3021100000011a272b9cb000000000000000000

1 output(s) for total of 59.341176251000 dcy

stealth address amount amount idx
00: 22ce05913ce970ae1caeb55ae2ab8af627c320a88a78170ecbb0121485b498e5 59.341176251000 638622 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": 306239, "vin": [ { "gen": { "height": 306229 } } ], "vout": [ { "amount": 59341176251, "target": { "key": "22ce05913ce970ae1caeb55ae2ab8af627c320a88a78170ecbb0121485b498e5" } } ], "extra": [ 1, 26, 117, 246, 127, 54, 248, 116, 43, 126, 109, 173, 200, 65, 225, 248, 187, 204, 10, 203, 243, 50, 110, 60, 175, 231, 181, 93, 212, 3, 4, 180, 163, 2, 17, 0, 0, 0, 17, 162, 114, 185, 203, 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