Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5773c1a442cf05604623c3f88b54d9559680e1b0b27fca3eded26a10a148c10

Tx prefix hash: 088457dd953f853557eae03054e7ff62c7c195edbc991000c6bc12d314c1dff2
Tx public key: 6bb9ad619fc5914f442244192cbdcba793f15ed7ac703de27b3e5a62de4b0b4f
Timestamp: 1728024313 Timestamp [UCT]: 2024-10-04 06:45:13 Age [y:d:h:m:s]: 00:161:08:52:04
Block: 1124085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115132 RingCT/type: yes/0
Extra: 016bb9ad619fc5914f442244192cbdcba793f15ed7ac703de27b3e5a62de4b0b4f02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d57b1289dddfc246c0ec62e60f1ee93c5f52fd8c2ac195803cf6e5988dbd0236 0.600000000000 1606652 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": 1124095, "vin": [ { "gen": { "height": 1124085 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d57b1289dddfc246c0ec62e60f1ee93c5f52fd8c2ac195803cf6e5988dbd0236" } } ], "extra": [ 1, 107, 185, 173, 97, 159, 197, 145, 79, 68, 34, 68, 25, 44, 189, 203, 167, 147, 241, 94, 215, 172, 112, 61, 226, 123, 62, 90, 98, 222, 75, 11, 79, 2, 17, 0, 0, 0, 2, 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