Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 391d41c71e6bba2e7459d2e268f53cc81ffb8707602ad54300dc3caecffec0fc

Tx prefix hash: 473af73d38bc6c5a0792576ad79748efb585d6b30428f8a28d7957edbe0d1fc5
Tx public key: ac6fe33d99ea8e0c622b5a1e0895650826bce9e704248a2d22c776424b51da63
Timestamp: 1701537452 Timestamp [UCT]: 2023-12-02 17:17:32 Age [y:d:h:m:s]: 01:162:19:20:00
Block: 904488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377533 RingCT/type: yes/0
Extra: 01ac6fe33d99ea8e0c622b5a1e0895650826bce9e704248a2d22c776424b51da6302110000000146113aa8000000000000000000

1 output(s) for total of 0.618095756000 dcy

stealth address amount amount idx
00: 90fc89d469bb8613806f1870bb2b696a99abae60bf2c88b77d3c708b31eb6c24 0.618095756000 1361247 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": 904498, "vin": [ { "gen": { "height": 904488 } } ], "vout": [ { "amount": 618095756, "target": { "key": "90fc89d469bb8613806f1870bb2b696a99abae60bf2c88b77d3c708b31eb6c24" } } ], "extra": [ 1, 172, 111, 227, 61, 153, 234, 142, 12, 98, 43, 90, 30, 8, 149, 101, 8, 38, 188, 233, 231, 4, 36, 138, 45, 34, 199, 118, 66, 75, 81, 218, 99, 2, 17, 0, 0, 0, 1, 70, 17, 58, 168, 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