Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f14617c91074c77347f89a1330dbaa218bfa178acea7c8b9c7980c521cfe89a

Tx prefix hash: bb6adfa386c317a41b9a09d4eaaff6a6eb6c4d6b721383089daa1bbbb0a13451
Tx public key: 0f3502a7eeb3fc8ffbc95c15392dc4c837a3d0c2683edb42f88cdda7e3b577d4
Timestamp: 1725620400 Timestamp [UCT]: 2024-09-06 11:00:00 Age [y:d:h:m:s]: 00:227:15:34:21
Block: 1104155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162542 RingCT/type: yes/0
Extra: 010f3502a7eeb3fc8ffbc95c15392dc4c837a3d0c2683edb42f88cdda7e3b577d402110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9783e90e4d3cdfa73e693c6ed5d49048989914403c40a061ecc03513811168d4 0.600000000000 1581234 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": 1104165, "vin": [ { "gen": { "height": 1104155 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9783e90e4d3cdfa73e693c6ed5d49048989914403c40a061ecc03513811168d4" } } ], "extra": [ 1, 15, 53, 2, 167, 238, 179, 252, 143, 251, 201, 92, 21, 57, 45, 196, 200, 55, 163, 208, 194, 104, 62, 219, 66, 248, 140, 221, 167, 227, 181, 119, 212, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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