Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bc24e7bdb64012fddab59dc086d3d062abe90ca071169b88559ac86b7e2f429

Tx prefix hash: a90daf6b731e001d3e0948179d8a9e01c850e6f97b81cf5e033c6218b4fcc249
Tx public key: a02f95333f610d8726b5a3711d009e9656761d143d0ab5ce0a717e6cfdf14744
Timestamp: 1718565571 Timestamp [UCT]: 2024-06-16 19:19:31 Age [y:d:h:m:s]: 00:161:01:02:58
Block: 1045680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115243 RingCT/type: yes/0
Extra: 01a02f95333f610d8726b5a3711d009e9656761d143d0ab5ce0a717e6cfdf1474402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a028ec1a288e068d1753f96abdc5eadb3b16dbba49e71336d37530ba59b3584 0.600000000000 1515315 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": 1045690, "vin": [ { "gen": { "height": 1045680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a028ec1a288e068d1753f96abdc5eadb3b16dbba49e71336d37530ba59b3584" } } ], "extra": [ 1, 160, 47, 149, 51, 63, 97, 13, 135, 38, 181, 163, 113, 29, 0, 158, 150, 86, 118, 29, 20, 61, 10, 181, 206, 10, 113, 126, 108, 253, 241, 71, 68, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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