Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 169789be5374d9f8e131e0d4096ac8d04072975ca2c34c8a260dd87d093b8541

Tx prefix hash: eb2e5a643ede2bb712cf3553b80b422e678e6bac834e0e8cfc2971958e4dcef9
Tx public key: 2f1de9ccf8c09039358307a8c7e8a5f03b135af1b179f38a945eeefbfdab4ab5
Timestamp: 1675345398 Timestamp [UCT]: 2023-02-02 13:43:18 Age [y:d:h:m:s]: 02:002:01:02:30
Block: 688222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523037 RingCT/type: yes/0
Extra: 012f1de9ccf8c09039358307a8c7e8a5f03b135af1b179f38a945eeefbfdab4ab50211000000015029cbac000000000000000000

1 output(s) for total of 3.218360949000 dcy

stealth address amount amount idx
00: 719d1956409ef2aa59eecd056c0bc125199e1c4cc01dcdaee0110779c7c5c873 3.218360949000 1130830 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": 688232, "vin": [ { "gen": { "height": 688222 } } ], "vout": [ { "amount": 3218360949, "target": { "key": "719d1956409ef2aa59eecd056c0bc125199e1c4cc01dcdaee0110779c7c5c873" } } ], "extra": [ 1, 47, 29, 233, 204, 248, 192, 144, 57, 53, 131, 7, 168, 199, 232, 165, 240, 59, 19, 90, 241, 177, 121, 243, 138, 148, 94, 238, 251, 253, 171, 74, 181, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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