Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c7c5a4b4ffab70e4e6b6082f3feb1436aa2e28fdcc31c98cde2c7f90f479243

Tx prefix hash: ee7ced101d4f064aa3cb98a7c59423afcb151f5b729256b35dcfe0e8aed0dcef
Tx public key: da179f6e6820bbb5da63b598a7ddb49e364c009f0c0544228db3cd6788c9df6b
Timestamp: 1638368432 Timestamp [UCT]: 2021-12-01 14:20:32 Age [y:d:h:m:s]: 03:163:15:33:15
Block: 386144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 895679 RingCT/type: yes/0
Extra: 01da179f6e6820bbb5da63b598a7ddb49e364c009f0c0544228db3cd6788c9df6b021100000001f6cc1430000000000000000000

1 output(s) for total of 32.251135041000 dcy

stealth address amount amount idx
00: 95c20d2f2e6aade0b04a16ca1ccf4650dfec18427ebbcd109493be5dc809449c 32.251135041000 779101 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": 386154, "vin": [ { "gen": { "height": 386144 } } ], "vout": [ { "amount": 32251135041, "target": { "key": "95c20d2f2e6aade0b04a16ca1ccf4650dfec18427ebbcd109493be5dc809449c" } } ], "extra": [ 1, 218, 23, 159, 110, 104, 32, 187, 181, 218, 99, 181, 152, 167, 221, 180, 158, 54, 76, 0, 159, 12, 5, 68, 34, 141, 179, 205, 103, 136, 201, 223, 107, 2, 17, 0, 0, 0, 1, 246, 204, 20, 48, 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