Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddc5eef3e39298631fa8e44a7a036412ddc04ee6840c8e72f13b542673ad55f6

Tx prefix hash: c47530c32f4ae024b10cce90e00f779514d4c70dc76604a618aa5b8e59974463
Tx public key: 83e1942dca825e57f1b92241746b9ad6392ea4f69387fec5cbb8201217e0f1df
Timestamp: 1725072812 Timestamp [UCT]: 2024-08-31 02:53:32 Age [y:d:h:m:s]: 00:219:05:57:02
Block: 1099610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156544 RingCT/type: yes/0
Extra: 0183e1942dca825e57f1b92241746b9ad6392ea4f69387fec5cbb8201217e0f1df02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e638a593cdc9a08f1d7faf22dc4beda7ce8466ad22b9bdb44fb7567c916ae18 0.600000000000 1575575 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": 1099620, "vin": [ { "gen": { "height": 1099610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e638a593cdc9a08f1d7faf22dc4beda7ce8466ad22b9bdb44fb7567c916ae18" } } ], "extra": [ 1, 131, 225, 148, 45, 202, 130, 94, 87, 241, 185, 34, 65, 116, 107, 154, 214, 57, 46, 164, 246, 147, 135, 254, 197, 203, 184, 32, 18, 23, 224, 241, 223, 2, 17, 0, 0, 0, 9, 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