Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e373ddf99b1884e0c33f1d1793f13ccb73ee0b93e8c635e7a12a7421019b1f1a

Tx prefix hash: 2716b086b9d62881f540e54f7bd403f76e6efab0b6a88597ecb708051f918569
Tx public key: c85951d2c1260d55f6c823557031e04dcb7a0cbc37c776c3c3c1021d56edd62d
Timestamp: 1706398878 Timestamp [UCT]: 2024-01-27 23:41:18 Age [y:d:h:m:s]: 01:009:17:57:16
Block: 944766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268030 RingCT/type: yes/0
Extra: 01c85951d2c1260d55f6c823557031e04dcb7a0cbc37c776c3c3c1021d56edd62d02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ade7c41ded569121b105ef74546b78a6e971545feeadeb9f68d0d29a9090a173 0.600000000000 1403052 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": 944776, "vin": [ { "gen": { "height": 944766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ade7c41ded569121b105ef74546b78a6e971545feeadeb9f68d0d29a9090a173" } } ], "extra": [ 1, 200, 89, 81, 210, 193, 38, 13, 85, 246, 200, 35, 85, 112, 49, 224, 77, 203, 122, 12, 188, 55, 199, 118, 195, 195, 193, 2, 29, 86, 237, 214, 45, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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