Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b2d2276f3a873fa37316af9f2669a99abf6e11310111dc4ebdb158184f7a469

Tx prefix hash: 95e16a22e2065fd7248d288cd0bd0611b80b74d32841c7c7ce0ddfb2b3073a96
Tx public key: bbe19c33250162f1426c5901c376485e71854c2e945658ab2c9ebefc8b76ec5b
Timestamp: 1681566059 Timestamp [UCT]: 2023-04-15 13:40:59 Age [y:d:h:m:s]: 02:061:16:53:17
Block: 739160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 566204 RingCT/type: yes/0
Extra: 01bbe19c33250162f1426c5901c376485e71854c2e945658ab2c9ebefc8b76ec5b02110000000475e3f0e9000000000000000000

1 output(s) for total of 2.182007802000 dcy

stealth address amount amount idx
00: 44177b82fe1700db4d4cc09c87a67f873db729e5f5fb9706ace1b122a45f38c1 2.182007802000 1185983 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": 739170, "vin": [ { "gen": { "height": 739160 } } ], "vout": [ { "amount": 2182007802, "target": { "key": "44177b82fe1700db4d4cc09c87a67f873db729e5f5fb9706ace1b122a45f38c1" } } ], "extra": [ 1, 187, 225, 156, 51, 37, 1, 98, 241, 66, 108, 89, 1, 195, 118, 72, 94, 113, 133, 76, 46, 148, 86, 88, 171, 44, 158, 190, 252, 139, 118, 236, 91, 2, 17, 0, 0, 0, 4, 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