Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2f0d1e81f196784994454bd7813dd2c48007ecd99b4b2419ae93c06f5275225

Tx prefix hash: 5f646f0a1f0769a145078a59c05ec94bfc5cdd8aa26107a68f78df79c0c0ecd5
Tx public key: 3b60ecc12ce2c4c0e338eee35cf57fa182ace7ccb3cec405af0236fc1a74eb64
Timestamp: 1641063838 Timestamp [UCT]: 2022-01-01 19:03:58 Age [y:d:h:m:s]: 02:332:07:38:17
Block: 408349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 755622 RingCT/type: yes/0
Extra: 013b60ecc12ce2c4c0e338eee35cf57fa182ace7ccb3cec405af0236fc1a74eb64021100000001edb0d4a3000000000000000000

1 output(s) for total of 27.225169260000 dcy

stealth address amount amount idx
00: 0d04b462768f86ec9219a89f7bde8f2737eedbb77b602540526cfd0f8411d7f5 27.225169260000 810348 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": 408359, "vin": [ { "gen": { "height": 408349 } } ], "vout": [ { "amount": 27225169260, "target": { "key": "0d04b462768f86ec9219a89f7bde8f2737eedbb77b602540526cfd0f8411d7f5" } } ], "extra": [ 1, 59, 96, 236, 193, 44, 226, 196, 192, 227, 56, 238, 227, 92, 245, 127, 161, 130, 172, 231, 204, 179, 206, 196, 5, 175, 2, 54, 252, 26, 116, 235, 100, 2, 17, 0, 0, 0, 1, 237, 176, 212, 163, 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