Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f6f12e0c6e079faffdb5612cc1f0f2f04741cdf601ffd299903917924f3d5af

Tx prefix hash: 3b469747c91093b472abca3ba55bdaf106573be36eab0142feaf6de7a74e03da
Tx public key: 36c40e8f945439bbd0473cecd7f6d0e249dac8a747e5a9b96335e2f93a46ca8c
Timestamp: 1721742839 Timestamp [UCT]: 2024-07-23 13:53:59 Age [y:d:h:m:s]: 00:259:19:34:47
Block: 1071994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185617 RingCT/type: yes/0
Extra: 0136c40e8f945439bbd0473cecd7f6d0e249dac8a747e5a9b96335e2f93a46ca8c021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 134aee038548007ef7429afe90932f4a1160e2390a7e3d7e9ed35277a58136e1 0.600000000000 1544409 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": 1072004, "vin": [ { "gen": { "height": 1071994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "134aee038548007ef7429afe90932f4a1160e2390a7e3d7e9ed35277a58136e1" } } ], "extra": [ 1, 54, 196, 14, 143, 148, 84, 57, 187, 208, 71, 60, 236, 215, 246, 208, 226, 73, 218, 200, 167, 71, 229, 169, 185, 99, 53, 226, 249, 58, 70, 202, 140, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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