Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c41a2aa41b5408346ad7a465b1da08d973c77398e1fb5decff131fe48732f775

Tx prefix hash: f4271ba1e63fe881af56ba6b393e40f8942e14d4a3aab152fe5695e0acba91ef
Tx public key: 046e2f0aba80654323c5b34fb44c398cbcc44e411e56e8ee1840b8abd3211409
Timestamp: 1706511909 Timestamp [UCT]: 2024-01-29 07:05:09 Age [y:d:h:m:s]: 01:139:01:39:10
Block: 945709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360409 RingCT/type: yes/0
Extra: 01046e2f0aba80654323c5b34fb44c398cbcc44e411e56e8ee1840b8abd32114090211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8fcb1059d6db5fe95d9a952c4c7c51ba8492e60226c0e3f40e5162db75f3af1b 0.600000000000 1404027 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": 945719, "vin": [ { "gen": { "height": 945709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fcb1059d6db5fe95d9a952c4c7c51ba8492e60226c0e3f40e5162db75f3af1b" } } ], "extra": [ 1, 4, 110, 47, 10, 186, 128, 101, 67, 35, 197, 179, 79, 180, 76, 57, 140, 188, 196, 78, 65, 30, 86, 232, 238, 24, 64, 184, 171, 211, 33, 20, 9, 2, 17, 0, 0, 0, 1, 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