Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf302513922bd55847c796346cc98f841ba8035a4e5dfea485d06df0a17a6365

Tx prefix hash: 95d81ea467c4f44b765fe7ad33db374fef222f10fe5a231c9523fb8b016965d4
Tx public key: a51f7eb7b1b08fee84ba8d1c252cfeda5ec15f7aa7d7c8a1305f440813861e88
Timestamp: 1738933155 Timestamp [UCT]: 2025-02-07 12:59:15 Age [y:d:h:m:s]: 00:286:05:59:05
Block: 1214091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202339 RingCT/type: yes/0
Extra: 01a51f7eb7b1b08fee84ba8d1c252cfeda5ec15f7aa7d7c8a1305f440813861e88021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48f64c367492d845d8d42251a51d2580c36948d926d760f1f49f0bcba61906cb 0.600000000000 1700876 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": 1214101, "vin": [ { "gen": { "height": 1214091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48f64c367492d845d8d42251a51d2580c36948d926d760f1f49f0bcba61906cb" } } ], "extra": [ 1, 165, 31, 126, 183, 177, 176, 143, 238, 132, 186, 141, 28, 37, 44, 254, 218, 94, 193, 95, 122, 167, 215, 200, 161, 48, 95, 68, 8, 19, 134, 30, 136, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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