Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0763af2009d6fc45dddd1405171259f3d2db9b0456168a83bf727f1c7ef2255d

Tx prefix hash: c16fdd6d9dbff1aea36d40471803d20268137ce1fd9c6303a7dfe394ad7ae5c9
Tx public key: dd11434c20b1ac9fe599094e686d0666d53bf6e8e94f4de5f86227acc2842a01
Timestamp: 1671155553 Timestamp [UCT]: 2022-12-16 01:52:33 Age [y:d:h:m:s]: 02:324:04:55:51
Block: 653504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 751114 RingCT/type: yes/0
Extra: 01dd11434c20b1ac9fe599094e686d0666d53bf6e8e94f4de5f86227acc2842a010211000000057e406890000000000000000000

1 output(s) for total of 4.194400988000 dcy

stealth address amount amount idx
00: f48c608c8c5d09f46a94224482e08ac53352b3a318503ef6a521b18d8ec3ccc5 4.194400988000 1093969 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": 653514, "vin": [ { "gen": { "height": 653504 } } ], "vout": [ { "amount": 4194400988, "target": { "key": "f48c608c8c5d09f46a94224482e08ac53352b3a318503ef6a521b18d8ec3ccc5" } } ], "extra": [ 1, 221, 17, 67, 76, 32, 177, 172, 159, 229, 153, 9, 78, 104, 109, 6, 102, 213, 59, 246, 232, 233, 79, 77, 229, 248, 98, 39, 172, 194, 132, 42, 1, 2, 17, 0, 0, 0, 5, 126, 64, 104, 144, 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