Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddbb8ed165ec1a26297f8293f67f734f6c910f143c1b537f9923ccd85562bce2

Tx prefix hash: 6f46e775ef1cec8d196c62b9899807027498ccb31fd6b662b7cf00a227cf2504
Tx public key: 4fc20a61a0219c1b1b6a0179de11bb92ba34e54288fa7faa8a0503d5d95f9c58
Timestamp: 1632852964 Timestamp [UCT]: 2021-09-28 18:16:04 Age [y:d:h:m:s]: 03:212:14:17:59
Block: 342678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 928503 RingCT/type: yes/0
Extra: 014fc20a61a0219c1b1b6a0179de11bb92ba34e54288fa7faa8a0503d5d95f9c5802110000000236fe6557000000000000000000

1 output(s) for total of 44.933056769000 dcy

stealth address amount amount idx
00: 3ae39bfdb53e56a5c993628915eb8670ef2f20a6a8b01e1b27d557b95c2ab3ed 44.933056769000 703676 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": 342688, "vin": [ { "gen": { "height": 342678 } } ], "vout": [ { "amount": 44933056769, "target": { "key": "3ae39bfdb53e56a5c993628915eb8670ef2f20a6a8b01e1b27d557b95c2ab3ed" } } ], "extra": [ 1, 79, 194, 10, 97, 160, 33, 156, 27, 27, 106, 1, 121, 222, 17, 187, 146, 186, 52, 229, 66, 136, 250, 127, 170, 138, 5, 3, 213, 217, 95, 156, 88, 2, 17, 0, 0, 0, 2, 54, 254, 101, 87, 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