Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 977de71ef8968821d372e2c1a06469958ee87246c9007f6717a0115f2476c016

Tx prefix hash: 3151b981c2503b95e796509dcee4aa911fd8a2fafc8d4e058c7f4cd190e2ecc5
Tx public key: a10ae09003f03d6d58646a8cac6b0ef6105c43d905e93137e3cf3fa6b842c664
Timestamp: 1729611076 Timestamp [UCT]: 2024-10-22 15:31:16 Age [y:d:h:m:s]: 00:032:16:05:39
Block: 1137202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23339 RingCT/type: yes/0
Extra: 01a10ae09003f03d6d58646a8cac6b0ef6105c43d905e93137e3cf3fa6b842c664021100000001991650d1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66cf5a59f0c80340ad2845194e089be29d816c6184c2d00ec7dc969f0f6d7f4b 0.600000000000 1620649 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": 1137212, "vin": [ { "gen": { "height": 1137202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66cf5a59f0c80340ad2845194e089be29d816c6184c2d00ec7dc969f0f6d7f4b" } } ], "extra": [ 1, 161, 10, 224, 144, 3, 240, 61, 109, 88, 100, 106, 140, 172, 107, 14, 246, 16, 92, 67, 217, 5, 233, 49, 55, 227, 207, 63, 166, 184, 66, 198, 100, 2, 17, 0, 0, 0, 1, 153, 22, 80, 209, 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