Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1a2daabf76984c47b260a18b78c4be30e382cf16d0816edf36be5b6b6fe1df8

Tx prefix hash: ee65567453abe6e35b5b87e92b9ca27229eb71e73ce96d8df5c11479d2ab2ccc
Tx public key: b6c4da83365044618a91ea47e651d6b0b42accce8a69126da4e87d00df3dce06
Timestamp: 1736514037 Timestamp [UCT]: 2025-01-10 13:00:37 Age [y:d:h:m:s]: 00:070:15:47:05
Block: 1194326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50272 RingCT/type: yes/0
Extra: 01b6c4da83365044618a91ea47e651d6b0b42accce8a69126da4e87d00df3dce060211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5449ecd87b29894ca557d54930d1856a4c2b0d731707bcbfd9ac47a8d57ebd44 0.600000000000 1680895 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": 1194336, "vin": [ { "gen": { "height": 1194326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5449ecd87b29894ca557d54930d1856a4c2b0d731707bcbfd9ac47a8d57ebd44" } } ], "extra": [ 1, 182, 196, 218, 131, 54, 80, 68, 97, 138, 145, 234, 71, 230, 81, 214, 176, 180, 42, 204, 206, 138, 105, 18, 109, 164, 232, 125, 0, 223, 61, 206, 6, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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