Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec92bade2485fc5cbbb47578e4b4b02e757717b890f1deab891299de531316e1

Tx prefix hash: e50f073b8651bbc233ee6bd015de8f7a28747de59ffe06e4314be3c342ca4a6e
Tx public key: f9bf8cb580068845f752f5611aec92c6c9982e090a7e659dc8bd7b951c92af9d
Timestamp: 1705538267 Timestamp [UCT]: 2024-01-18 00:37:47 Age [y:d:h:m:s]: 01:090:15:50:42
Block: 937636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325899 RingCT/type: yes/0
Extra: 01f9bf8cb580068845f752f5611aec92c6c9982e090a7e659dc8bd7b951c92af9d02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc929f115eb9a18b10d243483ae96e8fe02857d0b66a5d76bf0dc90a84545c85 0.600000000000 1395698 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": 937646, "vin": [ { "gen": { "height": 937636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc929f115eb9a18b10d243483ae96e8fe02857d0b66a5d76bf0dc90a84545c85" } } ], "extra": [ 1, 249, 191, 140, 181, 128, 6, 136, 69, 247, 82, 245, 97, 26, 236, 146, 198, 201, 152, 46, 9, 10, 126, 101, 157, 200, 189, 123, 149, 28, 146, 175, 157, 2, 17, 0, 0, 0, 5, 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