Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b1ebc150da48c7a7ddccbbc3ae309561ee4ecc66f1a820c9449dcee85719426

Tx prefix hash: e5812902cf034e29ff4079c8b894cc405df968d52dedcf732f76530d35f3e509
Tx public key: 4bcabf4d6a1d0590a507bfba988cd6a75dbf2e305ba895a1429835b9f9b0394e
Timestamp: 1717080997 Timestamp [UCT]: 2024-05-30 14:56:37 Age [y:d:h:m:s]: 00:267:03:09:28
Block: 1033352 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190873 RingCT/type: yes/0
Extra: 014bcabf4d6a1d0590a507bfba988cd6a75dbf2e305ba895a1429835b9f9b0394e02110000000341ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31bd0d416e32cfaf9e9412996ce74a11a86be13f7c7c1a99d60a07bacbb8ad9a 0.600000000000 1501817 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": 1033362, "vin": [ { "gen": { "height": 1033352 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31bd0d416e32cfaf9e9412996ce74a11a86be13f7c7c1a99d60a07bacbb8ad9a" } } ], "extra": [ 1, 75, 202, 191, 77, 106, 29, 5, 144, 165, 7, 191, 186, 152, 140, 214, 167, 93, 191, 46, 48, 91, 168, 149, 161, 66, 152, 53, 185, 249, 176, 57, 78, 2, 17, 0, 0, 0, 3, 65, 238, 28, 155, 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