Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8079ce713792ce603f0e3b67c529ef2ec46998297f64e326d6ed6d01623d5919

Tx prefix hash: 72390d63c20cd898a58f1d3e40c6b6e5b12c92adab5b8355eaa3ad2e42ecfb22
Tx public key: f6a7594fb3d778b4f957b241421054e70d7a97e06b1704aa7d68dc8fd989945e
Timestamp: 1579273233 Timestamp [UCT]: 2020-01-17 15:00:33 Age [y:d:h:m:s]: 04:340:18:31:12
Block: 47730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1132936 RingCT/type: yes/0
Extra: 01f6a7594fb3d778b4f957b241421054e70d7a97e06b1704aa7d68dc8fd989945e02110000000849b77a3d000000000000000000

1 output(s) for total of 426.471213795000 dcy

stealth address amount amount idx
00: 1d44c6ee4e3e26534edba8572ebffa5bce256cc5d13c0e3166d8ca0329af99f9 426.471213795000 88147 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": 47740, "vin": [ { "gen": { "height": 47730 } } ], "vout": [ { "amount": 426471213795, "target": { "key": "1d44c6ee4e3e26534edba8572ebffa5bce256cc5d13c0e3166d8ca0329af99f9" } } ], "extra": [ 1, 246, 167, 89, 79, 179, 215, 120, 180, 249, 87, 178, 65, 66, 16, 84, 231, 13, 122, 151, 224, 107, 23, 4, 170, 125, 104, 220, 143, 217, 137, 148, 94, 2, 17, 0, 0, 0, 8, 73, 183, 122, 61, 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