Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09cf272bf6eda2c957d2f1350b825a9088ee2a94fde469dc84d4f450b13f7018

Tx prefix hash: f527dbd79c41f8eb6e3b3fd855faee03cc56aa5e16486ece44be1beefc59fcf2
Tx public key: fb79c82373b96184a29cb87478d8eb6616899c3e678ae87601b5b0c1660b7c19
Timestamp: 1577787536 Timestamp [UCT]: 2019-12-31 10:18:56 Age [y:d:h:m:s]: 05:352:03:05:59
Block: 35631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1399250 RingCT/type: yes/0
Extra: 01fb79c82373b96184a29cb87478d8eb6616899c3e678ae87601b5b0c1660b7c190211000000044ac5aa02000000000000000000

1 output(s) for total of 467.671128686000 dcy

stealth address amount amount idx
00: 25dd905e46e2f2b8c5bdb19afcadc938a3e6e04a52f7325ecd7fb8d4576719fa 467.671128686000 60138 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": 35641, "vin": [ { "gen": { "height": 35631 } } ], "vout": [ { "amount": 467671128686, "target": { "key": "25dd905e46e2f2b8c5bdb19afcadc938a3e6e04a52f7325ecd7fb8d4576719fa" } } ], "extra": [ 1, 251, 121, 200, 35, 115, 185, 97, 132, 162, 156, 184, 116, 120, 216, 235, 102, 22, 137, 156, 62, 103, 138, 232, 118, 1, 181, 176, 193, 102, 11, 124, 25, 2, 17, 0, 0, 0, 4, 74, 197, 170, 2, 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