Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 613a5cfb26e06dfa6b18cc0e4093fe7adcaecd680c3397811e120472c83bbaf3

Tx prefix hash: 6251746e4cc38fdf2bd67df8c7c73c2d380b6678af2ecb6e1d11ab5a640053ce
Tx public key: b4263434bc3eb8724a7e321ca05ea2dc54e3d9f824f97d1cabe9affee3079165
Timestamp: 1733628506 Timestamp [UCT]: 2024-12-08 03:28:26 Age [y:d:h:m:s]: 00:131:12:05:09
Block: 1170444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93794 RingCT/type: yes/0
Extra: 01b4263434bc3eb8724a7e321ca05ea2dc54e3d9f824f97d1cabe9affee3079165021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d297d79d6db2a51780cf89dfc26aa366165dc19dbd7952f8559aa74466a9f13a 0.600000000000 1656175 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": 1170454, "vin": [ { "gen": { "height": 1170444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d297d79d6db2a51780cf89dfc26aa366165dc19dbd7952f8559aa74466a9f13a" } } ], "extra": [ 1, 180, 38, 52, 52, 188, 62, 184, 114, 74, 126, 50, 28, 160, 94, 162, 220, 84, 227, 217, 248, 36, 249, 125, 28, 171, 233, 175, 254, 227, 7, 145, 101, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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