Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 866d458c205c981407a24dc63cf18451491acaae7e7963e0b9fad02c3ae82c60

Tx prefix hash: b5e67614335651c69d8605e95da11e1ac6899b71579d66f5dcadf60aee894fc3
Tx public key: 704b58c5bec4239cd799d10ce22b030af05ea908a18a57175945b2671aea914b
Timestamp: 1700444177 Timestamp [UCT]: 2023-11-20 01:36:17 Age [y:d:h:m:s]: 01:142:12:42:14
Block: 895428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363041 RingCT/type: yes/0
Extra: 01704b58c5bec4239cd799d10ce22b030af05ea908a18a57175945b2671aea914b021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.662331357000 dcy

stealth address amount amount idx
00: a17e420c7a51dea7cfb0c5a6276229a8d3edc943cba70d4fe28854ee29740c98 0.662331357000 1351665 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": 895438, "vin": [ { "gen": { "height": 895428 } } ], "vout": [ { "amount": 662331357, "target": { "key": "a17e420c7a51dea7cfb0c5a6276229a8d3edc943cba70d4fe28854ee29740c98" } } ], "extra": [ 1, 112, 75, 88, 197, 190, 196, 35, 156, 215, 153, 209, 12, 226, 43, 3, 10, 240, 94, 169, 8, 161, 138, 87, 23, 89, 69, 178, 103, 26, 234, 145, 75, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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