Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f121f0bc6a5cd644760cefd63c9a62d0fcf2d300610c3b7e100289f3339f00c

Tx prefix hash: 0c2317c4da532c51c69781bef007b26c874559e7e12ec4ce66ba2d6fbe7a0703
Tx public key: 865dc4949781ca2fa754c116d2e8629a0eccf673faeac2cf2f25817ec58a411a
Timestamp: 1698518320 Timestamp [UCT]: 2023-10-28 18:38:40 Age [y:d:h:m:s]: 01:153:13:20:32
Block: 879677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370732 RingCT/type: yes/0
Extra: 01865dc4949781ca2fa754c116d2e8629a0eccf673faeac2cf2f25817ec58a411a02110000000433af99f4000000000000000000

1 output(s) for total of 0.746904268000 dcy

stealth address amount amount idx
00: ca497bfc74e9e7f8416efe69b4f14c94f6810340e3efc4b3ad8f7cb32647749c 0.746904268000 1335211 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": 879687, "vin": [ { "gen": { "height": 879677 } } ], "vout": [ { "amount": 746904268, "target": { "key": "ca497bfc74e9e7f8416efe69b4f14c94f6810340e3efc4b3ad8f7cb32647749c" } } ], "extra": [ 1, 134, 93, 196, 148, 151, 129, 202, 47, 167, 84, 193, 22, 210, 232, 98, 154, 14, 204, 246, 115, 250, 234, 194, 207, 47, 37, 129, 126, 197, 138, 65, 26, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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