Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf115fadf041df8fad1bdd55d44c03c9f09a25d711161c8c147c3159900b9f3d

Tx prefix hash: fde587bafdb4d090fc8b9b99cc1608b1f68c1fe89e41f381d8fbdaa1658232f6
Tx public key: b42644fbc03fa85da667f616efec2030e66b982aa93fa80ba7b5f2d29071ce44
Timestamp: 1727297977 Timestamp [UCT]: 2024-09-25 20:59:37 Age [y:d:h:m:s]: 00:150:13:43:45
Block: 1118061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107384 RingCT/type: yes/0
Extra: 01b42644fbc03fa85da667f616efec2030e66b982aa93fa80ba7b5f2d29071ce4402110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ccbaf90d17c1d1cf428d3b847ff8c3e5b24d1f101d3747fb722072114510bf65 0.600000000000 1599124 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": 1118071, "vin": [ { "gen": { "height": 1118061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ccbaf90d17c1d1cf428d3b847ff8c3e5b24d1f101d3747fb722072114510bf65" } } ], "extra": [ 1, 180, 38, 68, 251, 192, 63, 168, 93, 166, 103, 246, 22, 239, 236, 32, 48, 230, 107, 152, 42, 169, 63, 168, 11, 167, 181, 242, 210, 144, 113, 206, 68, 2, 17, 0, 0, 0, 7, 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