Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ccbf1c6e8591400fd1e273b2ee099eeea76cf516ff0b275d81bd73e6b92beb9

Tx prefix hash: de74b0a94c9d768f523dcb56ff8a9fa1a80f48e83c18bc3be2b464c80addd575
Tx public key: 0bc6efe52cf4db684a7b1b7840ec1f3f30d2fc9c10f56990ceaf2de9de18e59c
Timestamp: 1763660156 Timestamp [UCT]: 2025-11-20 17:35:56 Age [y:d:h:m:s]: 00:005:20:21:02
Block: 1416385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4191 RingCT/type: yes/0
Extra: 010bc6efe52cf4db684a7b1b7840ec1f3f30d2fc9c10f56990ceaf2de9de18e59c02110000000770609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f6e108943365464dcc4d53cd7f494dd4cba336bff83d138b0f74494bbb7adce 0.600000000000 1904904 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": 1416395, "vin": [ { "gen": { "height": 1416385 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f6e108943365464dcc4d53cd7f494dd4cba336bff83d138b0f74494bbb7adce" } } ], "extra": [ 1, 11, 198, 239, 229, 44, 244, 219, 104, 74, 123, 27, 120, 64, 236, 31, 63, 48, 210, 252, 156, 16, 245, 105, 144, 206, 175, 45, 233, 222, 24, 229, 156, 2, 17, 0, 0, 0, 7, 112, 96, 157, 3, 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