Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d067c3ebac1bf77d763bb22a2b235436d51616cb1c56563f6d404447986f1ffc

Tx prefix hash: b933386ddefba8ffb13c59888f50edf7270c957c3f4baacc38f36504f9d71fe5
Tx public key: 514dece569dec033ce0159b93df1df5095d1aad015bb1d8ee429f8fc5f0e0cee
Timestamp: 1631721625 Timestamp [UCT]: 2021-09-15 16:00:25 Age [y:d:h:m:s]: 04:047:05:10:28
Block: 334397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1067789 RingCT/type: yes/0
Extra: 01514dece569dec033ce0159b93df1df5095d1aad015bb1d8ee429f8fc5f0e0cee0211000000013fc41461000000000000000000

1 output(s) for total of 47.864320218000 dcy

stealth address amount amount idx
00: 1e0bb733de29fa2e7900be7fcb961ff90a3554ac7053959a97aae8f669c13134 47.864320218000 689744 of 0

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": 334407, "vin": [ { "gen": { "height": 334397 } } ], "vout": [ { "amount": 47864320218, "target": { "key": "1e0bb733de29fa2e7900be7fcb961ff90a3554ac7053959a97aae8f669c13134" } } ], "extra": [ 1, 81, 77, 236, 229, 105, 222, 192, 51, 206, 1, 89, 185, 61, 241, 223, 80, 149, 209, 170, 208, 21, 187, 29, 142, 228, 41, 248, 252, 95, 14, 12, 238, 2, 17, 0, 0, 0, 1, 63, 196, 20, 97, 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