Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1126f993837a2f8018a4d2bb101aa0e8c082854df588cef39558a79a462b4b0e

Tx prefix hash: ba1a008e1083d3bc904bb96f4999ed63a2d2ba369659a61a82199cbdb29013fd
Tx public key: 8aa69deb724de0d12b0e5fd96c48f42070113649a64fc981ea4345a75f9a15fc
Timestamp: 1724636040 Timestamp [UCT]: 2024-08-26 01:34:00 Age [y:d:h:m:s]: 00:224:15:53:28
Block: 1095978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160427 RingCT/type: yes/0
Extra: 018aa69deb724de0d12b0e5fd96c48f42070113649a64fc981ea4345a75f9a15fc02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cb8fff1cf8422d9cc33480a97b6c44ade4431c99beaabdc01c5c2e3e1837ff6 0.600000000000 1571165 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": 1095988, "vin": [ { "gen": { "height": 1095978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cb8fff1cf8422d9cc33480a97b6c44ade4431c99beaabdc01c5c2e3e1837ff6" } } ], "extra": [ 1, 138, 166, 157, 235, 114, 77, 224, 209, 43, 14, 95, 217, 108, 72, 244, 32, 112, 17, 54, 73, 166, 79, 201, 129, 234, 67, 69, 167, 95, 154, 21, 252, 2, 17, 0, 0, 0, 7, 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