Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44d325f477c9ea739a18f35eb9cdb76c3e1353db3679d8907a07ac878137573c

Tx prefix hash: f98c069135e9249f4dc9b8b7f7723bd41273c79cfa707cf3fc168f7f462bcac6
Tx public key: cb3a60c9f54ce7038ba827d127ab900cc5b59cecd4aaec6984c92499525d5f1b
Timestamp: 1669272108 Timestamp [UCT]: 2022-11-24 06:41:48 Age [y:d:h:m:s]: 02:186:15:29:56
Block: 637889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 655160 RingCT/type: yes/0
Extra: 01cb3a60c9f54ce7038ba827d127ab900cc5b59cecd4aaec6984c92499525d5f1b02110000000183600029000000000000000000

1 output(s) for total of 4.725077618000 dcy

stealth address amount amount idx
00: 136c60cd5c806b0f83b6be4d0bda2f1a368944f45765ae1c94015ca25eb23819 4.725077618000 1077480 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": 637899, "vin": [ { "gen": { "height": 637889 } } ], "vout": [ { "amount": 4725077618, "target": { "key": "136c60cd5c806b0f83b6be4d0bda2f1a368944f45765ae1c94015ca25eb23819" } } ], "extra": [ 1, 203, 58, 96, 201, 245, 76, 231, 3, 139, 168, 39, 209, 39, 171, 144, 12, 197, 181, 156, 236, 212, 170, 236, 105, 132, 201, 36, 153, 82, 93, 95, 27, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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