Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e2290819004732908c12615d85500648cd4dad1670d32d1fa43a59bbcafa278

Tx prefix hash: e6a3cce3e44d175b5f3737c1bd45f65ac252a27b863cd0c30f9490ca3a999c9c
Tx public key: 174fbf64e99a7802b0ebd818ed9414e7642ed172359e1f0c69c6a0b6f18654cd
Timestamp: 1579113471 Timestamp [UCT]: 2020-01-15 18:37:51 Age [y:d:h:m:s]: 05:021:19:57:48
Block: 46210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1165772 RingCT/type: yes/0
Extra: 01174fbf64e99a7802b0ebd818ed9414e7642ed172359e1f0c69c6a0b6f18654cd0211000000138a2ee0d9000000000000000000

1 output(s) for total of 431.407733268000 dcy

stealth address amount amount idx
00: 219bd43970a327e29677f328126e9c768fbf118246f23c8dfb0e6543afea48b5 431.407733268000 84896 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": 46220, "vin": [ { "gen": { "height": 46210 } } ], "vout": [ { "amount": 431407733268, "target": { "key": "219bd43970a327e29677f328126e9c768fbf118246f23c8dfb0e6543afea48b5" } } ], "extra": [ 1, 23, 79, 191, 100, 233, 154, 120, 2, 176, 235, 216, 24, 237, 148, 20, 231, 100, 46, 209, 114, 53, 158, 31, 12, 105, 198, 160, 182, 241, 134, 84, 205, 2, 17, 0, 0, 0, 19, 138, 46, 224, 217, 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