Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbca04d1446e645250b7f2777c6969cff76f8bfc7259f095e19a37ed4551a99f

Tx prefix hash: e9b21add6a57012f200cd1ce425c22bcea2e69b45e28a4efe5b9a56f26479ad3
Tx public key: 05cfb6d8de069158386757652ceeda71b6417aad777574fd337f01a652024bee
Timestamp: 1673448123 Timestamp [UCT]: 2023-01-11 14:42:03 Age [y:d:h:m:s]: 02:091:07:56:51
Block: 672485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 586955 RingCT/type: yes/0
Extra: 0105cfb6d8de069158386757652ceeda71b6417aad777574fd337f01a652024bee0211000000048b7b6602000000000000000000

1 output(s) for total of 3.628924951000 dcy

stealth address amount amount idx
00: c983a660f0f63d9a8f1f623d1b9cf7f0e1f1b942a61a915ae0f03953f14a7fcd 3.628924951000 1114036 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": 672495, "vin": [ { "gen": { "height": 672485 } } ], "vout": [ { "amount": 3628924951, "target": { "key": "c983a660f0f63d9a8f1f623d1b9cf7f0e1f1b942a61a915ae0f03953f14a7fcd" } } ], "extra": [ 1, 5, 207, 182, 216, 222, 6, 145, 88, 56, 103, 87, 101, 44, 238, 218, 113, 182, 65, 122, 173, 119, 117, 116, 253, 51, 127, 1, 166, 82, 2, 75, 238, 2, 17, 0, 0, 0, 4, 139, 123, 102, 2, 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