Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de35f34b1a61b7dc08be1f7408b7a2d3f58e708f6094366089bcf5d2a7a13bc9

Tx prefix hash: 0f87ef3040d0c4fd5b7a9d83486beaf962828d27086a5fb1af4304bb0d5eb14f
Tx public key: c671791bdfea9ee575593c5cee5a90c45e36359c11ec25f558b32cb3f09a3e41
Timestamp: 1715210237 Timestamp [UCT]: 2024-05-08 23:17:17 Age [y:d:h:m:s]: 00:349:22:54:10
Block: 1017851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250143 RingCT/type: yes/0
Extra: 01c671791bdfea9ee575593c5cee5a90c45e36359c11ec25f558b32cb3f09a3e410211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 961f5ab19f6657bddeb42e8526bde24ebf0deed19f87090a60536a1aac9acdbc 0.600000000000 1481636 of 15

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": 1017861, "vin": [ { "gen": { "height": 1017851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "961f5ab19f6657bddeb42e8526bde24ebf0deed19f87090a60536a1aac9acdbc" } } ], "extra": [ 1, 198, 113, 121, 27, 223, 234, 158, 229, 117, 89, 60, 92, 238, 90, 144, 196, 94, 54, 53, 156, 17, 236, 37, 245, 88, 179, 44, 179, 240, 154, 62, 65, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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