Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 395150fcf0b4220167d87ebd19d3caf86a3b9aa9c9f8a96d42f463dd45771535

Tx prefix hash: 621e028803ecbee9b4f9d62d1bc9ed086e2d4c60fe2d714dd1edce5a403c2fed
Tx public key: b0a7cab96a738df28ae857822f360f1d8f9d79906a173cef5bc44e212db3afbf
Timestamp: 1717277293 Timestamp [UCT]: 2024-06-01 21:28:13 Age [y:d:h:m:s]: 00:297:14:57:44
Block: 1034996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212679 RingCT/type: yes/0
Extra: 01b0a7cab96a738df28ae857822f360f1d8f9d79906a173cef5bc44e212db3afbf021100000003679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75f9b889c99a46163671f517017c33f62bcf20f0cb9a8d479e2b8cf242b2b50f 0.600000000000 1503515 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": 1035006, "vin": [ { "gen": { "height": 1034996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75f9b889c99a46163671f517017c33f62bcf20f0cb9a8d479e2b8cf242b2b50f" } } ], "extra": [ 1, 176, 167, 202, 185, 106, 115, 141, 242, 138, 232, 87, 130, 47, 54, 15, 29, 143, 157, 121, 144, 106, 23, 60, 239, 91, 196, 78, 33, 45, 179, 175, 191, 2, 17, 0, 0, 0, 3, 103, 154, 138, 129, 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