Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 944ee725ed63ecacaea39e40a4ce2073d2d23fab7907c1a29b061c5600e41f98

Tx prefix hash: 2a195915683b87c4d1907d6db816072b15a76ee4c0aa708d78f396f14a62a9d5
Tx public key: feb009497c8bd2799de45e4908e822641bd0dc15fa2eaa51d034c83bc24c1ec1
Timestamp: 1711012130 Timestamp [UCT]: 2024-03-21 09:08:50 Age [y:d:h:m:s]: 01:068:10:47:07
Block: 983061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309924 RingCT/type: yes/0
Extra: 01feb009497c8bd2799de45e4908e822641bd0dc15fa2eaa51d034c83bc24c1ec10211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df87bb1026181159a316dc3e8d7d23fbe5a0f6855a9f982d4dbfb2ee54450515 0.600000000000 1443180 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": 983071, "vin": [ { "gen": { "height": 983061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df87bb1026181159a316dc3e8d7d23fbe5a0f6855a9f982d4dbfb2ee54450515" } } ], "extra": [ 1, 254, 176, 9, 73, 124, 139, 210, 121, 157, 228, 94, 73, 8, 232, 34, 100, 27, 208, 220, 21, 250, 46, 170, 81, 208, 52, 200, 59, 194, 76, 30, 193, 2, 17, 0, 0, 0, 8, 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