Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8469892a73f06e8e65a8be12c2af97f96d94b6966e0c718c6d63f4d67276cc91

Tx prefix hash: 185936d1571ba21689adab7b752c1b4775bd555bdf8e422c77dbe698e847ebdc
Tx public key: 50c690b1197e13635c9f6c97b11a5a61292812806639a903b666ce322ac530b9
Timestamp: 1577846702 Timestamp [UCT]: 2020-01-01 02:45:02 Age [y:d:h:m:s]: 05:002:13:03:13
Block: 36113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151854 RingCT/type: yes/0
Extra: 0150c690b1197e13635c9f6c97b11a5a61292812806639a903b666ce322ac530b90211000000128a2ee0d9000000000000000000

1 output(s) for total of 465.954481524000 dcy

stealth address amount amount idx
00: 1f6b329ef1ca2b1bb56ffff03b9420e88257d38ecf4ae322770a9f576194506d 465.954481524000 61067 of 0

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": 36123, "vin": [ { "gen": { "height": 36113 } } ], "vout": [ { "amount": 465954481524, "target": { "key": "1f6b329ef1ca2b1bb56ffff03b9420e88257d38ecf4ae322770a9f576194506d" } } ], "extra": [ 1, 80, 198, 144, 177, 25, 126, 19, 99, 92, 159, 108, 151, 177, 26, 90, 97, 41, 40, 18, 128, 102, 57, 169, 3, 182, 102, 206, 50, 42, 197, 48, 185, 2, 17, 0, 0, 0, 18, 138, 46, 224, 217, 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