Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c8d72c906d1f69ebffd42fae67cf12046fbb5a6abee93a183971ddad3c61e95

Tx prefix hash: d0d04ea207b07657de13aaaf02c84595030c70d2b527b3f5d043b5361e430183
Tx public key: 2645c52a33f9f84e699604e9b1cab4a4e58f312c81221a09cbc48d7f03daeee2
Timestamp: 1675712063 Timestamp [UCT]: 2023-02-06 19:34:23 Age [y:d:h:m:s]: 02:096:17:06:50
Block: 691274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 590748 RingCT/type: yes/0
Extra: 012645c52a33f9f84e699604e9b1cab4a4e58f312c81221a09cbc48d7f03daeee20211000000045029cbac000000000000000000

1 output(s) for total of 3.144287163000 dcy

stealth address amount amount idx
00: 7786133242b2b2c8d084b9b44bd3764bcea5a45f49313a57df1fc0823e37deb7 3.144287163000 1134026 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": 691284, "vin": [ { "gen": { "height": 691274 } } ], "vout": [ { "amount": 3144287163, "target": { "key": "7786133242b2b2c8d084b9b44bd3764bcea5a45f49313a57df1fc0823e37deb7" } } ], "extra": [ 1, 38, 69, 197, 42, 51, 249, 248, 78, 105, 150, 4, 233, 177, 202, 180, 164, 229, 143, 49, 44, 129, 34, 26, 9, 203, 196, 141, 127, 3, 218, 238, 226, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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