Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 737846f67dba825a5e74f8f4121ce9409b0ff4fb2ba765ae84253b86d6fb8464

Tx prefix hash: c374b1c47f92e9a0d992d2b4da49ae740c866ceb351d171cba0a0fd17583b171
Tx public key: 314666b98903f6e52ef6ac9d6fd7576c621ff872f270b0a0dab349790c4032cf
Timestamp: 1706956758 Timestamp [UCT]: 2024-02-03 10:39:18 Age [y:d:h:m:s]: 01:277:06:04:12
Block: 949400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456928 RingCT/type: yes/0
Extra: 01314666b98903f6e52ef6ac9d6fd7576c621ff872f270b0a0dab349790c4032cf0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e36819c5df63c5ecc7ce54af76626b1c3e377b9735cc0dad237af90b8efa091 0.600000000000 1407924 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": 949410, "vin": [ { "gen": { "height": 949400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e36819c5df63c5ecc7ce54af76626b1c3e377b9735cc0dad237af90b8efa091" } } ], "extra": [ 1, 49, 70, 102, 185, 137, 3, 246, 229, 46, 246, 172, 157, 111, 215, 87, 108, 98, 31, 248, 114, 242, 112, 176, 160, 218, 179, 73, 121, 12, 64, 50, 207, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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