Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c646beb53c9d17fdd8ddb2fdc1e166a20351d85de418d3e1f127b60a9fe6ed40

Tx prefix hash: 256b2542f800eec62ac50c5ab19dccf318cac6bf10f09f18b44a392760b8e91d
Tx public key: 485c79ca5597abede841b931a1d0f3af61fc24c599ebee999ce0400dab6a4440
Timestamp: 1711577885 Timestamp [UCT]: 2024-03-27 22:18:05 Age [y:d:h:m:s]: 01:003:21:13:54
Block: 987748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263724 RingCT/type: yes/0
Extra: 01485c79ca5597abede841b931a1d0f3af61fc24c599ebee999ce0400dab6a444002110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c24b58a975bb64a8d3a1095a1a9d43f4e5941d1119f6065f5f665e23c96e6ca8 0.600000000000 1448007 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": 987758, "vin": [ { "gen": { "height": 987748 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c24b58a975bb64a8d3a1095a1a9d43f4e5941d1119f6065f5f665e23c96e6ca8" } } ], "extra": [ 1, 72, 92, 121, 202, 85, 151, 171, 237, 232, 65, 185, 49, 161, 208, 243, 175, 97, 252, 36, 197, 153, 235, 238, 153, 156, 224, 64, 13, 171, 106, 68, 64, 2, 17, 0, 0, 0, 11, 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