Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff6381819b47fb76f9dced90442516533673444f70a6e43d6010e7ce9cec6bde

Tx prefix hash: b323398f73051210dd196e0dfbfb3d8170887cc45ff00fcf12ab49932117c4f7
Tx public key: dca4e266854d0e2f2ad699844a706ae138e4ca53a07370183633a3aa685fa011
Timestamp: 1729578540 Timestamp [UCT]: 2024-10-22 06:29:00 Age [y:d:h:m:s]: 01:019:10:42:48
Block: 1136921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272297 RingCT/type: yes/0
Extra: 01dca4e266854d0e2f2ad699844a706ae138e4ca53a07370183633a3aa685fa011021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfd46097a4334ccb4e9bf6bb2a6a42dbb9da65caa2a3ae44646d2a4dc8fe0fa1 0.600000000000 1620318 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": 1136931, "vin": [ { "gen": { "height": 1136921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfd46097a4334ccb4e9bf6bb2a6a42dbb9da65caa2a3ae44646d2a4dc8fe0fa1" } } ], "extra": [ 1, 220, 164, 226, 102, 133, 77, 14, 47, 42, 214, 153, 132, 74, 112, 106, 225, 56, 228, 202, 83, 160, 115, 112, 24, 54, 51, 163, 170, 104, 95, 160, 17, 2, 17, 0, 0, 0, 2, 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