Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bc1ef70540ef97eeb38e0124b8c7d5f056cd6b996705ef6f8048bfa20bd80f8

Tx prefix hash: 43662b5882b052c1b617350578824264ea22b4d486c5c8bbf7180ca5cb75593c
Tx public key: cc2bb0df3e88833ab5bcc7447f4d21bf848bffe07e2ea7d5f79e5473773ca40d
Timestamp: 1724557022 Timestamp [UCT]: 2024-08-25 03:37:02 Age [y:d:h:m:s]: 00:150:12:02:05
Block: 1095355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107590 RingCT/type: yes/0
Extra: 01cc2bb0df3e88833ab5bcc7447f4d21bf848bffe07e2ea7d5f79e5473773ca40d021100000002e337358e000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87060e1027a21d7d0fd5743f56ccfcdd35965df0196cae68a3505b9e3b56b4f6 0.600000000000 1570522 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": 1095365, "vin": [ { "gen": { "height": 1095355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87060e1027a21d7d0fd5743f56ccfcdd35965df0196cae68a3505b9e3b56b4f6" } } ], "extra": [ 1, 204, 43, 176, 223, 62, 136, 131, 58, 181, 188, 199, 68, 127, 77, 33, 191, 132, 139, 255, 224, 126, 46, 167, 213, 247, 158, 84, 115, 119, 60, 164, 13, 2, 17, 0, 0, 0, 2, 227, 55, 53, 142, 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