Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f980a07a76cf0aa9ca88007f1727f22cb9363023d70671ffd6501ebd682a6f7

Tx prefix hash: ddbee40cf3e5d9a63379b6a317a3ebbb0dab0f476222c37f21ebf12f6afad5bd
Tx public key: 07730934583f8da230cb523134b9290f95e33a322daa7ec990b86cb415f00d3d
Timestamp: 1727603693 Timestamp [UCT]: 2024-09-29 09:54:53 Age [y:d:h:m:s]: 00:166:05:40:57
Block: 1120603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118611 RingCT/type: yes/0
Extra: 0107730934583f8da230cb523134b9290f95e33a322daa7ec990b86cb415f00d3d02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7d06711c1fbb7edb3911eb58917c0c346b776a8858edb354377cb62d148ac5a 0.600000000000 1602576 of 15

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": 1120613, "vin": [ { "gen": { "height": 1120603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7d06711c1fbb7edb3911eb58917c0c346b776a8858edb354377cb62d148ac5a" } } ], "extra": [ 1, 7, 115, 9, 52, 88, 63, 141, 162, 48, 203, 82, 49, 52, 185, 41, 15, 149, 227, 58, 50, 45, 170, 126, 201, 144, 184, 108, 180, 21, 240, 13, 61, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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