Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08cbbfb35c9a8886e8f5860194bdec34471d35478592c1db581f12f2768995d1

Tx prefix hash: 332c515fa941d82ced80a3b4ebed20c3767a8e2ea88e34b39b76f185ee88a78f
Tx public key: 2d25a7dcddc20f0b0a028921e017cc5321639b4f172f3ed48667df241e40c6eb
Timestamp: 1705106265 Timestamp [UCT]: 2024-01-13 00:37:45 Age [y:d:h:m:s]: 01:113:11:37:29
Block: 934057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342236 RingCT/type: yes/0
Extra: 012d25a7dcddc20f0b0a028921e017cc5321639b4f172f3ed48667df241e40c6eb02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f61d59f2b1989219415117f19406ee6bf6b5ae6ed17a35cca79e58587fab626 0.600000000000 1392043 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": 934067, "vin": [ { "gen": { "height": 934057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f61d59f2b1989219415117f19406ee6bf6b5ae6ed17a35cca79e58587fab626" } } ], "extra": [ 1, 45, 37, 167, 220, 221, 194, 15, 11, 10, 2, 137, 33, 224, 23, 204, 83, 33, 99, 155, 79, 23, 47, 62, 212, 134, 103, 223, 36, 30, 64, 198, 235, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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