Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bcb032e47e638715765fae051a394652e73f8432ab1b4a739246a0df3cc1deb

Tx prefix hash: ad8fa2bf5b1add8d4c909d5312aa6f4be041212a1d53a3a446477094ecacd09c
Tx public key: e5153e0c9129d5e15c4670fe75033920645f989335aa80e0a4a3e7dd6ec6dfa8
Timestamp: 1736928705 Timestamp [UCT]: 2025-01-15 08:11:45 Age [y:d:h:m:s]: 00:153:16:35:13
Block: 1197754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109548 RingCT/type: yes/0
Extra: 01e5153e0c9129d5e15c4670fe75033920645f989335aa80e0a4a3e7dd6ec6dfa802110000000f007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e56f568b35f3fd161ef95aa43444c502f075f0f975aaa3e5a319dbcb4614737c 0.600000000000 1684369 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": 1197764, "vin": [ { "gen": { "height": 1197754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e56f568b35f3fd161ef95aa43444c502f075f0f975aaa3e5a319dbcb4614737c" } } ], "extra": [ 1, 229, 21, 62, 12, 145, 41, 213, 225, 92, 70, 112, 254, 117, 3, 57, 32, 100, 95, 152, 147, 53, 170, 128, 224, 164, 163, 231, 221, 110, 198, 223, 168, 2, 17, 0, 0, 0, 15, 0, 127, 151, 138, 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