Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95b6ec30d8047d5713820d596f4d87b34b1c3abd902fe0f097cb6fb1aa003fca

Tx prefix hash: d53837b67079bbea1601004ccd701929240f311d64cca3229fe8f9951f4e85f4
Tx public key: 86fe99b0a5312a0ef768cecb525b01bcfa227e32a536339ab6b41d5f7f19fb38
Timestamp: 1706327510 Timestamp [UCT]: 2024-01-27 03:51:50 Age [y:d:h:m:s]: 01:079:03:56:47
Block: 944177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317672 RingCT/type: yes/0
Extra: 0186fe99b0a5312a0ef768cecb525b01bcfa227e32a536339ab6b41d5f7f19fb380211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4c72cc0a0acbd5ed242528daa176221b6e18a2a6f02cc312eb54cb3f13fcf44 0.600000000000 1402411 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": 944187, "vin": [ { "gen": { "height": 944177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4c72cc0a0acbd5ed242528daa176221b6e18a2a6f02cc312eb54cb3f13fcf44" } } ], "extra": [ 1, 134, 254, 153, 176, 165, 49, 42, 14, 247, 104, 206, 203, 82, 91, 1, 188, 250, 34, 126, 50, 165, 54, 51, 154, 182, 180, 29, 95, 127, 25, 251, 56, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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