Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af7e3ee4934859076c725711b22253068327b65257743e861113de8ee162f118

Tx prefix hash: 423b81abfd44e9b6d104acb3e5b483a77b964d66af9c900f1e9898329c70d16c
Tx public key: 6d03c3d909f4b7d6316041815ec7ac6a5c8723e608f4957b31d7799bc09558e1
Timestamp: 1726332846 Timestamp [UCT]: 2024-09-14 16:54:06 Age [y:d:h:m:s]: 01:055:14:43:44
Block: 1110055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298162 RingCT/type: yes/0
Extra: 016d03c3d909f4b7d6316041815ec7ac6a5c8723e608f4957b31d7799bc09558e102110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 292ad84c3a5eece7df2f102e82c40613ad21ce6b9b912cb0e18f627c4cf50c50 0.600000000000 1588528 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": 1110065, "vin": [ { "gen": { "height": 1110055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "292ad84c3a5eece7df2f102e82c40613ad21ce6b9b912cb0e18f627c4cf50c50" } } ], "extra": [ 1, 109, 3, 195, 217, 9, 244, 183, 214, 49, 96, 65, 129, 94, 199, 172, 106, 92, 135, 35, 230, 8, 244, 149, 123, 49, 215, 121, 155, 192, 149, 88, 225, 2, 17, 0, 0, 0, 2, 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