Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c3cc7bc8806481d29738bab354b2e7647ca0b321e2611840c9745bc48733d98

Tx prefix hash: dca5dc463d38dfbd7bb32caf3df6b0be82bed212eb7c5ce834908fa15e3fde83
Tx public key: 58631bc57fb06bb178893248665231ce9d02dd9d1b92b13d4294c2c1aaa7a26a
Timestamp: 1577316331 Timestamp [UCT]: 2019-12-25 23:25:31 Age [y:d:h:m:s]: 04:330:08:11:52
Block: 31714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1125254 RingCT/type: yes/0
Extra: 0158631bc57fb06bb178893248665231ce9d02dd9d1b92b13d4294c2c1aaa7a26a021100000004ad433a0b000000000000000000

1 output(s) for total of 481.858154173000 dcy

stealth address amount amount idx
00: dbf5a0e1b5be937920c4255e62e17c12c469a7a5af27cd2ed8600fd45ff5a3e1 481.858154173000 52569 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": 31724, "vin": [ { "gen": { "height": 31714 } } ], "vout": [ { "amount": 481858154173, "target": { "key": "dbf5a0e1b5be937920c4255e62e17c12c469a7a5af27cd2ed8600fd45ff5a3e1" } } ], "extra": [ 1, 88, 99, 27, 197, 127, 176, 107, 177, 120, 137, 50, 72, 102, 82, 49, 206, 157, 2, 221, 157, 27, 146, 177, 61, 66, 148, 194, 193, 170, 167, 162, 106, 2, 17, 0, 0, 0, 4, 173, 67, 58, 11, 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