Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2edbb7c5426f7c8ec744c52a776637c9c153eaa8995c0e0670a0a0474a3841c

Tx prefix hash: 0f3d42dd9b602d24eb148c392a353170e4d0b734638074255d780b217bb507ed
Tx public key: 536fe3caf17280c05facb9f08aa90a5f640f475d9132b66cfbb3aeebcd8f6493
Timestamp: 1700566064 Timestamp [UCT]: 2023-11-21 11:27:44 Age [y:d:h:m:s]: 01:148:16:01:50
Block: 896433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367436 RingCT/type: yes/0
Extra: 01536fe3caf17280c05facb9f08aa90a5f640f475d9132b66cfbb3aeebcd8f649302110000000175e3f0e9000000000000000000

1 output(s) for total of 0.657272304000 dcy

stealth address amount amount idx
00: 7767f132bfe46ba40110734224ba7afbc1396fb3e31751c8e97e15e672e02f0d 0.657272304000 1352740 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": 896443, "vin": [ { "gen": { "height": 896433 } } ], "vout": [ { "amount": 657272304, "target": { "key": "7767f132bfe46ba40110734224ba7afbc1396fb3e31751c8e97e15e672e02f0d" } } ], "extra": [ 1, 83, 111, 227, 202, 241, 114, 128, 192, 95, 172, 185, 240, 138, 169, 10, 95, 100, 15, 71, 93, 145, 50, 182, 108, 251, 179, 174, 235, 205, 143, 100, 147, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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