Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cff1e3b33a6cafaf729892f1f1e06238644ffe1b6512154dc718017329a84653

Tx prefix hash: 9cfffc78e92e49a1dfdc4de4b5603d289abc4497a0db0aba4ab59c33fd6e6566
Tx public key: fc216406e29bc395f6a5abd519d2cba518da814392c29bd07542c2ef02ac97d4
Timestamp: 1725804724 Timestamp [UCT]: 2024-09-08 14:12:04 Age [y:d:h:m:s]: 00:214:00:52:13
Block: 1105677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152816 RingCT/type: yes/0
Extra: 01fc216406e29bc395f6a5abd519d2cba518da814392c29bd07542c2ef02ac97d4021100000004e914dd15000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: 03b1e843955e027eec5432b1be67a68a4464c1ed91aa83cf188a005d136f9339 0.608000000000 1583096 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": 1105687, "vin": [ { "gen": { "height": 1105677 } } ], "vout": [ { "amount": 608000000, "target": { "key": "03b1e843955e027eec5432b1be67a68a4464c1ed91aa83cf188a005d136f9339" } } ], "extra": [ 1, 252, 33, 100, 6, 226, 155, 195, 149, 246, 165, 171, 213, 25, 210, 203, 165, 24, 218, 129, 67, 146, 194, 155, 208, 117, 66, 194, 239, 2, 172, 151, 212, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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