Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0e9b3fbc0f9712770eb4f8c2ae38311b61bf2dbb01bf7e216561d5f66c09b26

Tx prefix hash: b02be3da2614b1a4faa6d02fcd0896de656bbea0a64f4331c5542e4c12656cb7
Tx public key: bbf8e113743d494cc4c432fdda0b94f612e835fa66e761ee74c110aff7049524
Timestamp: 1582442182 Timestamp [UCT]: 2020-02-23 07:16:22 Age [y:d:h:m:s]: 04:257:06:16:18
Block: 70814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1076299 RingCT/type: yes/0
Extra: 01bbf8e113743d494cc4c432fdda0b94f612e835fa66e761ee74c110aff7049524021100000001026b59f3000000000000000000

1 output(s) for total of 357.572922607000 dcy

stealth address amount amount idx
00: e286a031b9320b0d9134018ff08d5a5d304b51bea9abdab8ee56458aa69800b0 357.572922607000 130810 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": 70824, "vin": [ { "gen": { "height": 70814 } } ], "vout": [ { "amount": 357572922607, "target": { "key": "e286a031b9320b0d9134018ff08d5a5d304b51bea9abdab8ee56458aa69800b0" } } ], "extra": [ 1, 187, 248, 225, 19, 116, 61, 73, 76, 196, 196, 50, 253, 218, 11, 148, 246, 18, 232, 53, 250, 102, 231, 97, 238, 116, 193, 16, 175, 247, 4, 149, 36, 2, 17, 0, 0, 0, 1, 2, 107, 89, 243, 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