Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7159a3b2a1df713fb73499059c495b3c3a8c0261c555fe97736c064ea2f7c007

Tx prefix hash: 1dac4c1c38a7838e5c159c59d66f215a41edcdbfec53c1a444f1a1cdccd886e3
Tx public key: e7a6d1a090e6288c6519140bb4caf8b8211844fb8db07b53891c61afb7a3d32c
Timestamp: 1659578836 Timestamp [UCT]: 2022-08-04 02:07:16 Age [y:d:h:m:s]: 03:114:21:40:44
Block: 558220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 861940 RingCT/type: yes/0
Extra: 01e7a6d1a090e6288c6519140bb4caf8b8211844fb8db07b53891c61afb7a3d32c02110000000475e3f0e9000000000000000000

1 output(s) for total of 8.677318372000 dcy

stealth address amount amount idx
00: ac7cee0fc378eaf94ad964e04a5b0664d96cb13bfd919fb252e67e80d22c9fd0 8.677318372000 990282 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": 558230, "vin": [ { "gen": { "height": 558220 } } ], "vout": [ { "amount": 8677318372, "target": { "key": "ac7cee0fc378eaf94ad964e04a5b0664d96cb13bfd919fb252e67e80d22c9fd0" } } ], "extra": [ 1, 231, 166, 209, 160, 144, 230, 40, 140, 101, 25, 20, 11, 180, 202, 248, 184, 33, 24, 68, 251, 141, 176, 123, 83, 137, 28, 97, 175, 183, 163, 211, 44, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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